Description

The data label has changed from (DQ: 1) to (DQ: 3). Since I don't have an older copy of the MAST image that @bmorris3 used to make that test, I am not sure why. The new label seems in line with existing parser logic in that it uses EXTNUM instead of EXTVER to make the label, so not sure why it was 1 before.

Goal is to fix the test so it does not block unrelated PRs. I am not sure if you want me to refactor the DQ parser.

Filename: jw01895001004_07101_00001_nrca3_cal.fits
No.    Name      Ver    Type      Cards   Dimensions   Format
  0  PRIMARY       1 PrimaryHDU     347   ()
  1  SCI           1 ImageHDU       156   (2048, 2048)   float32
  2  ERR           1 ImageHDU        10   (2048, 2048)   float32
  3  DQ            1 ImageHDU        11   (2048, 2048)   int32 (rescales to uint32)
  4  AREA          1 ImageHDU         9   (2048, 2048)   float32
  5  VAR_POISSON    1 ImageHDU         9   (2048, 2048)   float32
  6  VAR_RNOISE    1 ImageHDU         9   (2048, 2048)   float32
  7  VAR_FLAT      1 ImageHDU         9   (2048, 2048)   float32
  8  ASDF          1 BinTableHDU     11   1R x 1C   [27021B]

Change log entry

• Is a change log needed? If yes, is it added to CHANGES.rst? If you want to avoid merge conflicts,
  list the proposed change log here for review and add to CHANGES.rst before merge. If no, maintainer
  should add a no-changelog-entry-needed label.

Checklist for package maintainer(s)

This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.

• Are two approvals required? Branch protection rule does not check for the second approval. If a second approval is not necessary, please apply the trivial label.
• Do the proposed changes actually accomplish desired goals? Also manually run the affected example notebooks, if necessary.
• Do the proposed changes follow the STScI Style Guides?
• Are tests added/updated as required? If so, do they follow the STScI Style Guides?
• Are docs added/updated as required? If so, do they follow the STScI Style Guides?
• Did the CI pass? If not, are the failures related?
• Is a milestone set? Set this to bugfix milestone if this is a bug fix and needs to be released ASAP; otherwise, set this to the next major release milestone. Bugfix milestone also needs an accompanying backport label.
• After merge, any internal documentations need updating (e.g., JIRA, Innerspace)?